fix: do not fail on closure of already closed Nexus repositories #477
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using the plugin in a "multi-stage" deployment, on the final job (using semantic-release) the
releaseStagingRepositoryOnMavenCentral
task is called. This task depends on thecloseStagingrepositoryOnMavenCentral
, but since the staging repo is closed on the previous CI job (the job that tries to upload and close the staging repo), the staging repo will be closed twice producing the following errors:This PR introduces a check in the
closeStagingrepositoryOnMavenCentral
that if the repository is already closed, skip the closing action, raising a warning saying that the closing task is skippedLet me know how does it sound :)